home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
300last.zip
/
300LAST.DOC
< prev
next >
Wrap
Text File
|
1992-08-09
|
9KB
|
199 lines
300 LAST
=================================
version 1.05 released 8/09/92
A public domain SysOp utility from the Charlatan's Cabin BBS
for SysOps of Wildcat! version 3.0x ONLY.
See VERSION HISTORY at the end of this document.
WHAT IT DOES:
-------------
300LAST generates and automatically "trims" a listing of your most recent
callers. If enabled, it will include Wildcat! automatic color codes in
any of its display files.
HOW IT WORKS:
-------------
Each time a caller logs off from one of your nodes, the file NODEINFO.DAT
is updated to contain the caller's name, city, and time/date of logoff.
300LAST is run immediately after each logoff ... we'll explain how to do
that in a moment.
The 300LAST.CFG (configuration file) tells 300LAST where to find certain
files and what output files to write. Only ONE copy is required, anywhere
in your DOS path.
The program determines the node number by first checking to see if the
environment variable "WCNODEID=" is set. If so, it uses that value. If
not, it next looks for DOOR.SYS in the current directory. Remember that
Wildcat! will place you in the appropriate NODE WORK directory when you
shell out, and DOOR.SYS will be written there, too.
The program gathers the data, places it at the FRONT of the caller log,
so that the most recent calls are first, and writes the output file(s).
If the file has accumulated the configured maximum number of callers,
then the entry at the end of the file (the oldest call) will be deleted,
so you never have to trim the output file by hand.
Any caller may view this log at any time if you set it up as a bulletin.
Remember that when you first start using 300LAST there will be only a few
calls until the list builds up ... so you might wish to start it a day or
two before you announce the fact that the files are available for viewing.
INSTALLATION:
-------------
Installing the program is easy.
1. Place 300LAST.EXE anywhere in your path so it can be run
from any directory. The program requires BRUN40.EXE
which you almost certainly already have. If not, it's
widely available, including my BBS ... see below.
2. In your STARTUP directory, create a file called POSTCALL.BAT. Wildcat!
will automatically detect it (or POSTCALL.RUN in the work directory ...
see your Wildcat! documentation)
Here's a sample of what it should say:
echo off
300LAST
exit
The "EXIT" line isn't actually required, but it's a safe way to ensure
that the shell will properly release control to Wildcat! if something
goes wrong.
IMPORTANT: If you have MAKEWILD set to TERMINATE instead of SHELL,
you must create individual files named POSTCALL.RUN in each of your
node work directories. The last line of each one must be changed from
'exit' as shown above to the name of the batch file to start the
particular Wildcat! node. Refer to the Wildcat! documentation for more
details on SHELL and TERMINATE options ...
3. Run MAKEWILD and make sure whether you're set to SHELL or TERMINATE, then
review step 2 above.
4. Anywhere in your DOS path, you'll create 300LAST.CFG. Here's an
example of 300LAST.CFG ... this one would be for use on NODE 2, and
it would be placed in the \WC30\WCWORK\NODE2 directory:
BBSNAME=The Charlatan's Cabin BBS
NODEINFO=C:\WC30\DATA\NODEINFO.DAT
SAVEFILE=C:\WC30\300LAST.DAT
KEEPER=300
EXCLUDE=MICHAEL CONLEY
WRITE=C:\WC30\WCPRO.BBS /SHOWNODE /CLS /COLOR
WRITE=C:\WC30\BULL\BULL22.BBS /SHOWNODE /CLS /COLOR
Leave NO blank lines above these entries -- the program
imports each one based upon its line number in this file.
Line 1 BBSNAME= is the name of your BBS for the listing header,
e.g., BBSNAME=The Charlatan's Cabin BBS
Line 2 NODEINFO= is the Drive and PathName to the node information
file, e.g., NODEINFO=C:\WC30\DATA\NODEINFO.DAT
Line 3 SAVEFILE= is the Drive and PathName of the file 300 LAST will
use to keep a reference copy of the callers list.
It will be maintained automatically by 300 LAST.
e.g., SAVEFILE=C:\WC30\300LAST.DAT
Line 4 KEEPER= tells the program how many callers to keep. Any
value from 2 to 300 is valid here, e.g., KEEPER=300
Line 5 EXCLUDE= tells the program any names (such as the sysop) to
exclude from the listings. If you don't want to
exclude anyone, put EXCLUDE=NONE on this line.
Lines 6 - 300 name the output files. They will ALL be written
if there is new "last caller." The format is
important -- see below:
Each line MUST begin with the phrase "WRITE=" followed by a
valid COMPLETE DOS drive/path/filename. Any number of these
filenames (up to 300) are executed by the program. After the
filename, leave a space and then any combination of the available
switches:
/SHOWNODE will include the Node number in the listing in the
display file.
/CLS will place a Wildcat! clear-screen code at the front of
the display file.
/COLOR will cause Wildcat! automatic color codes to be generated.
If the caller is not ANSI-compatible, these color codes
will NOT be displayed. In that way, one ".BBS" file will
suffice for BOTH your COLOR and your MONO callers.
OPTIONAL APPROACH:
------------------
If you'll be using WCPRO to generate a BULLETIN instead of the
[S]tatistics display for the main menu, or if you don't plan
to run WCPRO's statistics function at all, you might do this:
Run MAKEWILD and edit the MAIN MENU so that the default "S" command
(system statistics) becomes something like [L]...Log of recent callers.
Be sure to change the "hot key" letter on the menu definition page to
whatever letter you select.
Change the 300LAST.CFG file to create WCPRO.BBS in the startup
directory:
WRITE=c:\wc30\WCPRO.BBS
... and add whatever other bulletins you wish to write ...
(make whatever changes are required for your pathnames, and
as before, be sure to use the correct node number in each
config file.
You may include up to 300 WRITE= commands in the configuration file.
Problems, questions, suggestions:
---------------------------------
If you get a message from 300LAST saying something like
FILES IN USE - Retry ## of 50
this means that 300LAST thinks that another copy of 300LAST is running
on another node. If that's NOT TRUE, then it accidentally left over a
file called "300LAST.PUK" in your C:\ directory. You can FORCE the
program to execute by typing an 'F' at this time. It should start within
5 seconds after you press the 'F' key.
PROBLEMS, SUGGESTIONS:
======================
300LAST is public domain. I don't seek or accept any donations for this or
any of my other Wildcat! utility programs, including TODAYBBS, FLOP, MSTAT,
USTAT, and others.
I welcome suggestions, and will try to help (no guarantees) if there are
problems.
You may contact me at The Charlatan's Cabin BBS (213) 654-7337. Mention
your Wildcat! registration number in the comment and you'll be upgraded to
membership without the usually required registration by mail.
You may also leave a message via CompuServe (70250,220).
Please, NO VOICE CALLS. This isn't meant to be unfriendly, but with
the price of public domain software these days ... I just can't afford
to be "on call." I WILL respond to your questions via my BBS or CompuServe,
or via the Mustang Software registered SysOp BBS.
VERSION HISTORY:
=================
1.00 Compiled 8/01/91 First release version for Wildcat! 3.0
1.01 Compiled 9/07/91 Removed audible warnings if file access denied.
1.02 Compiled 9/29/91 Improved duplicate detection if node received
a call but nobody logged on.
1.05 Compiled 8/09/92 Added reporting of LOCAL logons unless the
caller's name is in the EXCLUDE list.